Performing this change so the vue3 migration script can modify all @input, @v-model of components without changing plain elements. This will reduce the number of vue3 compiler errors.

Commands run:

➤ yarn migrate
➤ git clean -fdx
➤ nvm use 20
➤ yarn

Signed-off-by: Phillip Rak <[email protected]>

Signed-off-by: Phillip Rak <[email protected]>

Signed-off-by: Phillip Rak <[email protected]>

…uex]

This only addresses the complaints made by the cli when running. There are still more instances of createLocalVue

https://stackoverflow.com/questions/66932839/typeerror-0-testutils-createlocalvue-is-not-a-function

This was noticed in the CLI when running Ctrl + C to exit the server process

…ore than once with DefinePlugin()

It appears to be an update in webpack 4 which we can disable with config.optimization.nodeEnv

Uncaught runtime errors:

ERROR

Catch all routes ("*") must now be defined using a param with a custom regexp. See more at https://next.router.vuejs.org/guide/migration/#removed-star-or-catch-all-routes. 

Signed-off-by: Phillip Rak <[email protected]>

Signed-off-by: Phillip Rak <[email protected]>

Signed-off-by: Phillip Rak <[email protected]>

Signed-off-by: Phillip Rak <[email protected]>

Signed-off-by: Phillip Rak <[email protected]>

Signed-off-by: Phillip Rak <[email protected]>

An error occurred logging in: proxy must report the same value for the non-writable, non-configurable property '"$ctx"'

Signed-off-by: Phillip Rak <[email protected]>

There's a new important change in behavior between Vue2 and Vue3 regarding emitting native events in custom components. I was noticing that AsyncButton was emitting two click events, even though it was specifying $event.stopPropagation(); & $event.preventDefault(); before emitting its own click event. It turns out that the only way to "override" a native event is to specify it in the emits option
If a native event (e.g., click) is defined in the emits option, the listener will now only listen to component-emitted click events and no longer respond to native click events.
https://vuejs.org/guide/components/events.html#declaring-emitted-events

Signed-off-by: Phillip Rak <[email protected]>

… when doing the router replacement in our extendApp code

Signed-off-by: Phillip Rak <[email protected]>

Signed-off-by: Phillip Rak <[email protected]>

Signed-off-by: Phillip Rak <[email protected]>

Signed-off-by: Phillip Rak <[email protected]>

Signed-off-by: Phillip Rak <[email protected]>

…erences fullPath from resolve()

This removes one of our console warnings

We may want to investigate further why we have to access it using ._value. This most likely should've been taken care of inside entry.js

…lue.trim

We weren't calling set anymore which meant we weren't using the correct key when setting the values in some places.

We had this `hasTabs` api which implicitly allowed a chart install override component to implicitly define tabs instead of just having the component define them explicitly.

This required prop drilling to work and it doesn't appear to work any longer with dynamic components. Since this was only used in two places I removed support for this and simplified the implementation.

I did this so I could change how that button is referenced in tests. I don't think we ever should've used the add-label attribute.

…rty reference the old id

… consistent with our upgraded library

It passes locally but not when running in CI. This may be a race condition so I'm reordering and waiting on certain conditions when checking titles.

It looks like the pages weren't refreshing between tests.

…deleting an admin

…til a modal showed up which prevented us from testing further

- updating selectors for the inputs
- adding another inheritAttrs: false

We got rid of reactivity when we remove Vue.set() I've added it back. In this case it's specifically to make the feature flags table reactive when activating and deactivating flags.

…for the correct features